Rename '[Jenkins]' in tab title to '- Jenkins' #10178

janfaracik · 2025-01-18T17:33:12Z

A hopefully small PR to rename [Jenkins] in the tab title to - Jenkins. Using a hyphen is more common across the web and feels a little more polished IMV compared to the square brackets.

Testing done

Pages feature '- Jenkins' in their tab title now

Proposed changelog entries

N/A

Proposed developer changelog entries

Rename '[Jenkins]' in tab title to '- Jenkins'

Proposed upgrade guidelines

N/A

Submitter checklist

Give feedback

The Jira issue, if it exists, is well-described.
The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
There is automated testing or an explanation as to why this change has no tests.
New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
For dependency updates, there are links to external changelogs and, if possible, full differentials.
For new APIs and extension points, there is a link to at least one consumer.
Options

Desired reviewers

@jenkinsci/sig-ux

Before the changes are marked as ready-for-merge:

Maintainer checklist

Give feedback

There are at least two (2) approvals for the pull request and no outstanding requests for change.
Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
Proper changelog labels are set so that the changelog can be generated automatically.
If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).
Options

timja · 2025-01-19T17:50:41Z

jenkinsci/email-ext-plugin#579 needs releasing first

Init

6195f2b

janfaracik requested a review from a team January 18, 2025 17:33

Update SearchTest.java

3b20b12

krisstern approved these changes Jan 19, 2025

View reviewed changes

timja added the on-hold This pull request depends on another event/release, and it cannot be merged right now label Jan 19, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Rename '[Jenkins]' in tab title to '- Jenkins' #10178

Rename '[Jenkins]' in tab title to '- Jenkins' #10178

janfaracik commented Jan 18, 2025

Submitter checklist

Maintainer checklist

timja commented Jan 19, 2025

Rename '[Jenkins]' in tab title to '- Jenkins' #10178

Are you sure you want to change the base?

Rename '[Jenkins]' in tab title to '- Jenkins' #10178

Conversation

janfaracik commented Jan 18, 2025

Testing done

Proposed changelog entries

Proposed developer changelog entries

Proposed upgrade guidelines

Submitter checklist

Desired reviewers

Maintainer checklist

timja commented Jan 19, 2025